home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Tech Arsenal 1
/
Tech Arsenal (Arsenal Computer).ISO
/
tek-06
/
login108.zip
/
TTMANUAL.TXT
< prev
Wrap
Text File
|
1992-09-25
|
15KB
|
324 lines
Tamalpais Technologies - The Login Checker (V1.08 (9-25-92))
Copyright (c) 1991, 1992 - All rights reserved
────────────────────────────────────────────────────────
Introduction
──────────────
One day, I was sitting at my desk at work (I am a MIS / Help Desk manager for
a major software company) when the phone rang. It was someone from the
Marketing deparment, they were in Excel in Windows and they could not print to
the printer, it gave them some error message. I explained to the person
(who has great Marketing skills but little computer skills) that the problem
most likely was due the fact that she had not logged in. This got me
thinking... This was the third call that day for a problem related to the fact
that the employee had not logged in. Of course I couldn't blame the employee,
the message that they were not logged in flashes by as the rest of their
AUTOEXEC.BAT file is executed.
I asked myself, why didn't Novell make the login.exe program check to see
if you logged in correctly and if not, ask you to try again?
So I dusted off my 'C' manuals, turned on my tunes on and got to work on trying
to correct this little problem. Hence, the birth of The Login Checker. I
implemented it at the company that I work for and after 3 weeks of not having
ANY calls related to not logging in (and having no one complain about any
problems with The Login Checker itself - could the first try be bug free??)
I decided that maybe others could benefit from this handy dandy tool. After
only 2 months over 200 people downloaded it from Compuserve, so I must have
been right!
After having it in place at work for a couple of months I noticed another
hidden benefit. Many of the employee's liked to add there login name after
the login call in their AUTOEXEC.BAT (saving them from having to type it in).
This was great for them but frustrating to the Help Desk staff because if you
wanted to do any work setting up there machine you had to either not login
(and miss whatever setup pertained to the network in their AUTOEXEC.BAT) or
change their AUTOEXEC.BAT and reboot. What a pain. With The Login Checker,
all we needed to do was press return at the PASSWORD: prompt and type in our
own login name and password instead. Life is good again and we go home
smiling now (most of the time!).
The Login Checker is simpler in design than most people think. The easiest
way to test it and use it is to simply copy the two files (TTLOGIN.EXE and
TTLOGIN.CFG) to the LOGIN directory and change your AUTOEXEC.BAT to use
TTLOGIN.EXE. If you ever feel the need to login using the regular Novell login,
you can always type LOGIN.EXE.
I hope you The Login Checker is as useful to you as it was to us. Many thanks
to all of you who have send me your comments on the program and those of you
who have joined our family of registered users. Please send me any comments
you have about the product, good or bad, and any ideas you have that would
improve it.
Description:
──────────────
The Login Checker is a program that is designed to check whether you have
logged into a Novell network or not. This is advantageous for several
reasons:
* Less typing and frustration when logging in.
* Less calls to the MIS / System Administration /
Help desk - because employees will know when they
type their login name or password incorrectly.
(Most of the time they do not know they did not
login because the login command is part of the
autoexec.bat file, so the 'Access denied' message
scrolls past before they can read it).
* If a station is set up to login with that person's
login name (I.E. LOGIN MIKE), pressing return with
TTLOGIN will ask you for the new login name, so that
if someone else wants to log in to that station (such
as System Administrators!) all the network commands in
the 'AUTOEXEC.BAT' file that requires network login
are still executed.
How to Use:
────────────
Copy the two files (TTLOGIN.EXE and TTLOGIN.CFG) into the F:\LOGIN directory
(you must be logged in as supervisor to do this). Then type (or add to your
`autoexec.bat' file):
ttlogin <LOGINNAME>
You will need to keep LOGIN.EXE in that same directory. You do need to be
in the \LOGIN directory to use this program. If you login without making
any mistakes, it will look and act just like regular LOGIN.EXE. If you
mistype your login name or password, The Login Checker will ask you if you
want to login again. This continues until you either login correctly or
answer no to the question.
For Experienced System Adminstrators:
──────────────────────────────────────────
System Adminstrators can easily give everyone access to TTLOGIN, without
having to modify everyone's machines. This is recommended for System
Adminstrators that have experience with DOS and Novell. If you do not
have much experience, you may want to use the method suggested above.
Here's how:
* Login as supervisor.
* Copy TTLOGIN.EXE and TTLOGIN.CFG into the F:\LOGIN directory.
* Using `attrib' or another utility, remove the
'READ ONLY' tag from Novell's LOGIN.EXE program.
* Rename the orginal LOGIN.EXE to another name:
REN LOGIN.EXE LGN.EXE
* Rename TTLOGIN to LOGIN.EXE:
REN TTLOGIN.EXE LOGIN.EXE
* Use an ASCII editor to change the first line in TTLOGIN.CFG to the
new name you gave Novell's LOGIN.EXE (LGN.EXE).
* Reset the `READ ONLY' attribute on Novells LOGIN.EXE (now LGN.EXE).
This makes it so that if anyone types LOGIN (or it is in an `autoexec.bat'
file), it will automatically call The Login Checker. Be careful NOT to delete
Novell's LOGIN.EXE. You will need that to log in.
If you want to login without using The Login Checker, simply type the new name
you gave Novell's (LGN.EXE).
System Adminstrators can also modify the second line, which may help to
explain to end users which file server they are logging into.
Registration:
────────────────
Register this product and you will receive:
* The very latest version (with extra features)
* Information on other Tam Tech products
* A clear conscience!
The Login Checker is shareware (give one to a friend!), but NOT freeware
You must register the copy (and pay the fee) to use it (we do want to eat!)
When you register the copy, Tamalpais Technologies will send you the latest
version. This copy will include all new features developed so far.
Some ideas we may include in the future are:
* The ability to check for more than one file server on a network
* Ability to explain to end users which server they are logging into
(Done, see above)
* New features that we dream up before you get it!
The cost is: (Simplified! It used to be so complicated!)
---------------------------------------------------
Smaller sites:
$25 per file server at site
---------------------------------------------------
Site License:
More than 6 file servers? Total price is $150.
Number of Servers Price
______________________________________________
1 $25
2 $50
3 $75
4 $100
5 $125
6 $150
More than 6 $150
To register the product, please send check, cash or money order to:
Tamalpais Technologies
PO Box 125
Larkspur, CA 94977
(For information or telephone order, call: (415) 927-0333)
You can print an order form for The Login Checker. With your printer
on, From the DOS command line type: `ORDER'
Paying through Compuserve
─────────────────────────
You can now register Login Checker through Compuserve! It will get billed
directly to your Compuserve account. Simply type GO SWREG and follow the
instructions. When they ask you for a 'Keyword', use `TamTech'.
Tamalpais Technologies Complete Satisfaction Guarentee ...
────────────────────────────────────────────────────────────
The Login Checker comes with a 60 day money day back
guarentee. If you are unhappy with the product for any reason,
Tamalpais Technologies will refund your money in full. Simply call or
write TamTech with 60 days of purchase.
Suggestions / Support:
─────────────────────────
We welcome suggestions for improved features for The Login Checker, as well as
ideas for new utilities you'd like to see. We already have some idea's we are
playing with for future releases, such as automatic path correction (so that
when you logout your path is returned to it's healthy state), message ability
- so that the System Administrator can notify the user what server they are
logging into, etc.
To contact us, write us at the above address, send us a Compuserve Email (to
73257,2166) or call Tamalpais Technologies at (415) 927-0333. We would like
to here from you, so please do write or call us and tell us your complements,
problems, or new feature ideas.
Disclaimer:
────────────────
This software has been tested thoroughly and is believed to be free of
problems, however, software is one of the most complicated kind of product
produced by humans. No person can be absolutely and completely certain that a
piece of complicated software will work in any given machine and environment.
Therefore, you are completely responsible for determining the fitness of this
program and Tamalpais Technologies and it's staff are not liable for any damages.
Product Revision History:
─────────────────────────────
Revision History:
****** Version Release Date Change
****** -------------------------------------------------
****** 1.00 8-17-91 First release
****** No Bugs yet ....
****** (I'm closing my ears!)
****** ....................................................................
****** 1.01 9-11-91 * First Registered version
******
****** * Added the feature that allows you to
****** use the same login name again.
******
****** * Removed the 'ESC for info' line for
****** Registered users.
****** ....................................................................
****** 1.02 12-13-91 * Added pop up boxes for the info
****** * Removed the `Tamalpais Technologies' message
****** * Changed it so that the directory in the
****** login script is where you end up after
****** using TTlogin.
****** * Changed it so that you can login from
****** any directory even though you are already logged
****** in.
****** * Included reading TTLOGIN.CFG - Reads
****** Date info, Program Name, Info Line, Reg information
****** This version requires TTLOGIN.CFG in the Login directory
******
****** ....................................................................
****** 1.03 2-10-92 * Fixed the display bug created by reading in the lines of
****** of text wrong from TTLOGIN.CFG
****** * Now writes "Logging into" before the server line
****** if no name was typed in as a argument.
****** ....................................................................
****** 1.04 2-21-92 * Trying to fix the problem in where the
****** Login Checker conflicts with the programs
****** being executed from the System Login Script.
****** (Problem was NOT fixed, it still conflicts with
****** the 'exit' command in the login script).
****** (This version was never released)
****** .....................................................................
****** 1.05 3-16-92 * Allows more than one argument to be passed
****** to LOGIN.EXE (You can have up to five now).
******
****** * Created a way for customers to get rid of the
****** line "Logging into" if they would like.
****** They remove everything from line 2 in TTLOGIN.CFG
****** (make sure there are no spaces) and it will
****** eliminate that line.
******
****** 1.06 6-16-92 * When you used the 'Drive C:' command in
****** the login script, the login checker
****** tell you that you logged in
****** incorrectly. This is fixed now.
******
****** 1.07 7-05-92 * Increased the speed of the program when you
****** type in the incorrect password or login name.
****** Also fixed the problem when using the
****** EXIT command in the login script (I think!)
****** Solved ALL problems related to new drive
****** and or directory mappings.
******
****** 1.08 9-25-92 * Color was not being displayed correctly
****** after you left The Login Checker. It now
****** goes back to your original color.
******
****** ____________________________________________________________________
****** Known bugs:
******
****** * If you type in the Login Checker from a directory
****** other than where the CFG file is located, it will not
****** find it. This will be fixed in the next version.
******
******
**********************************************************************************
*********************************************************************************